Intelligent Delivery Agent for Short Message Distribution Center

ABSTRACT

A message distribution center (MDC) and Intelligent Delivery Agent are implemented in a wireless Internet gateway interposed between content providers and a wireless carrier to subjectively examine and direct messages via SMTP based on desired rules (e.g., non-peak hours, paying subscribers only, etc.) using standard SMTP Gateway and other well-known protocols. The MDC includes an individual queue for each subscriber, and the provider is informed through conventional SMTP protocol messages that the short message has been accepted. If the carrier has specifically disallowed service for a particular MIN (e.g., in the case of churning), then the content provider is informed through an SMTP interchange that the recipient is invalid. An MDC provides a single mechanism for interacting with subscribers of multiple carriers, regardless of each carrier&#39;s underlying infrastructure. For the carrier, an MDC can protect their SS7 network by intelligently throttling messages and configuring message delivery parameters to be more network friendly. An MDC can receive outside a relevant wireless network recipient handset presence information. In the disclosed embodiment, a content provider communicates with the MDC using SMTP protocol messages, and the MDC communicates with wireless carriers preferably using RMI/SMPP techniques.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless carriers, Internet serviceproviders (ISPs), and information content delivery services/providers.More particularly, it relates to Wireless Telecommunication, ANSI-41DWireless Intelligent Network (WIN) applications, and SMTP protocol tomanage information content for a wireless carrier.

2. Background of Related Art

There are many “wireless” information content providers in the industrywho have some information or service that is considered of value to themobile phone user. Wireless Carriers are typically in favor of thesecontent providers as they add value to Short Messaging Systems (SMS) andcan drive up SMS and voice usage.

Unfortunately, content providers may not fully understand a particularwireless network and/or may not be fully sensitized to particular needsof carriers. This is because the carrier is often seen simply as a‘pipe’ through which wireless messages are sent using SMTP protocol.Content providers maintain their own subscriber lists, and typicallycommunicate with carriers merely as e-mail hosts.

All traffic is typically sent through an SMTP gateway, and thusinformation content, ads, etc., cannot be differentiated from higherpriority ‘personal’ content. Problems arising from this include:

-   -   Bulk information content can slow down and even jeopardize the        carrier's SMTP Gateway performance;    -   Personal messages cannot be given a higher priority than bulk        messages;    -   Bulk info content receives the same messaging parameters as        personal messages, e.g., delivery receipts enabled, expiration        date of 3-5 days, etc.;    -   The carrier cannot differentiate between bulk messages among        various providers and personal mail for billing purposes;    -   Bulk senders deliver their content regardless of whether the        device is on, and thus the carrier must handle message storage        and retry attempts; and    -   Bulk senders will typically continue to deliver content to        churned wireless subscribers, wasting network resources and        interfering with reuse of mobile numbers.

There is a need for a technique using SMTP and/or other conventionalprotocols to enable an easy way for content providers to distributeand/or differentiate their information without requiring them to changetechnologies.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent tothose skilled in the art from the following description with referenceto the drawings, in which:

FIG. 1 shows a high level sequence diagram including a MessageDistribution Center (MDC) enabling a Content Provider to direct messagesvia SMTP to the Message Distribution Center (MDC), in accordance withthe principles of the present invention.

FIG. 2 illustrates exemplary software components and their relationshipsin an embodiment of a message distribution center (MDC), in accordancewith one embodiment of the present invention.

FIG. 3 is an exemplary class diagram which shows further details of anembodiment of a Message Distribution Center, in accordance with theprinciples of the present invention.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a messagedistribution center is interposed between a source of a short messageand a wireless network including an intended recipient of the shortmessage. The message distribution center comprises an SMTP protocolcommunication channel to receive the short message from the source ofthe short message. A plurality of subscriber queues are included, eachcorresponding to a different subscriber in the wireless network. Theshort message is placed in at least one of the plurality of subscriberqueues before delivery to the wireless network. A communication channelcommunicates the short message to the wireless network.

In accordance with another aspect of the present invention, a method ofthrottling short messages to subscribers in a wireless network comprisesforwarding a short message to a wireless network only when a receivingwireless device in said wireless network is known outside said wirelessnetwork to be online.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention enables a Content Provider to direct messages viaSMTP to an intermediatary Message Distribution Center (MDC) usingstandard SMTP Gateway and other well-known protocols.

In accordance with the principles of the present invention, shortmessages are inserted in the MDC into individual queues for eachsubscriber, and the provider is informed through conventional SMTPprotocol messages that the short message has been accepted.

If the carrier has specifically disallowed service for a MIN (e.g., inthe case of churning), then the content provider is informed through anSMTP interchange that the recipient is invalid. This encouragesproviders to discontinue service to terminated MINs, thereby reducingtraffic to the MDC.

A Message Distribution Center (MDC) provides value to both wirelessdevelopers and wireless carriers. For instance, for the WirelessDeveloper, an MDC provides a single mechanism for interacting withsubscribers of multiple carriers, regardless of each carrier'sunderlying infrastructure. For the carrier, an MDC can protect their SS7network by intelligently throttling messages and configuring messagedelivery parameters to be more network friendly.

An MDC acts as a broker between carriers and developers. Differentlevels of relationships can be established with both carriers anddevelopers, resulting in different levels of services that areavailable. The MDC interacts with a carrier's Short Message ServiceCenter(s) (SMSCs) and/or SS7 network, allowing developers to guaranteemessage delivery, to interact with users via Mobile Terminated (MT) andMobile Originated (MO) SMS, and possibly even to receive handsetpresence information.

Although the disclosed embodiments relate primarily to wireless servicesfrom the perspective of a Short Message Service (SMS), the disclosed MDCand related management middleware may support many types of wirelessdevices using the same API. For instance, suitable supported devices mayinclude, e.g., 2-way Email pagers, the Palm VII™, and wirelessapplication protocol (WAP) devices.

The disclosed MDC utilizes a Wireless Internet Gateway (WIG), which is amiddleware messaging platform designed to facilitate communicationbetween Internet devices and various wireless networks. A suitable WIGis disclosed in U.S. application Ser. No. 09/630,762 to SMITH, entitled“Wireless Internet Gateway”, filed Aug. 2, 2000, the entirety of whichis expressly incorporated herein by reference.

FIG. 1 shows a high level sequence diagram including a MessageDistribution Center (MDC) enabling a Content Provider to direct messagesvia SMTP to the Message Distribution Center (MDC), in accordance withthe principles of the present invention.

In particular, as shown in FIG. 1, an MDC gateway (MDC) 100 andIntelligent Delivery Agent (IDA) 318 are placed intermediary between acontent provider 120 and a wireless carrier 130, to allow management ofmessage delivery for each of a plurality of subscribers.

There are two main programs. The first application program is the MDCGateway 100, which is essentially a Wireless Internet Gateway to checkfor and process information provider messages as shown and describedherein. The second application program is the Intelligent Delivery Agent(IDA) 318,

As shown in FIG. 1, the content provider 120 communicates with the MDC100 using SMTP protocol messages, and the MDC communicates with thewireless carrier 130 preferably using RMI/SMPP techniques. A pluralityof configuration files 500 configured by an appropriate systemadministrator control parameters in the MDC 100 and IDA 318.

Importantly, the MDC 100 includes a plurality of subscriber queues 150,preferably one for each subscriber having MDC support. The subscriberqueues 150 may be integrated within the gateway of the MDC 100, or maybe external to the gateway of the MDC 100 but nevertheless in directcommunication with the gateway of the MDC 100.

The subscriber queue 150 preferably follows a First In First Out (FIFO)model, where the oldest messages are delivered first.

In accordance with the principles of the present invention, a particularwireless carrier 130 assigns a value for the maximum number ofoutstanding messages for a particular subscriber. This maximum number ofoutstanding messages can be used to establish a queue threshold. Thus,if one or more new messages cause the queue threshold to be exceeded,then the oldest messages may be deleted first from the particularsubscriber queue 150 to make room for the new message(s). Of course, thesubscriber queue 150 may be expanded in size as desired.

To provide protection from constantly growing subscriber queues 150,other rules may be established by the wireless carrier 130 to allowautomatic deletion of particular messages from the subscriber queue 150.

For instance, an expiration period may be established whereby allmessages more than x days old are removed. The expiration period may beestablished, e.g., on an individual subscriber basis (e.g., differentsubscription plans allowing larger queues and/or longer storage times),or on a global basis (e.g., all subscribers in a particular wirelessnetwork have a similar expiration time).

The use of automatic deletion of short messages from subscriber queues150 is important, e.g., in the case of churned MINs, so that a newsubscriber does not receive lingering messages from a previoussubscriber with the same MIN.

Short messages to subscriber queues 150 may be delivered independentlyfrom one another and/or message delivery times spaced apart, therebydistributing message load over time and minimizing the negative effectsof batch messaging on the wireless network.

The MDC 100 can also or alternatively be configured to avoid sendingbatch messages during the carrier's busy hour(s), thereby minimizingload pressures on the wireless network.

The use of an MDC 150 can aid the wireless carrier's networksignificantly, e.g., by forwarding short messages only when the relativehandsets are turned on. Under this scenario, subscriber queues are notprocessed when the handset is powered off. This can reduce networkstorage requirements, delivery retry attempts, and overall SS7 usage.The MDC 100 can do this either by interacting with appropriateapplications, e.g., with a mobile chat location register (MCLR), orgenerally by intelligent use of SMS delivery receipt data from the SMSCand Web Gateway. A suitable mobile chat location register (MCLR) isshown and described in U.S. application Ser. No. 09/814,363, entitled“Wireless Chat Automatic Status Tracking”, filed Mar. 23, 2001 by Ung etal., the entirety of which is expressly incorporated herein byreference.

The MDC 100 can further be configured to send content from variousproviders to certain SMPP ports on a short message service center(SMSC). The receipt of such content allows distinct billing records tobe generated for each type of service, e.g., ads, general content,premium content, etc.

FIG. 2 illustrates exemplary software components and their relationshipsin an embodiment of a message distribution center (MDC), in accordancewith one embodiment of the present invention.

In the disclosed embodiments, a Wireless Internet Gateway (WIG) wasmodified to include another ‘dev/null’ destination, which acknowledgesshort messages from a queueMonitor, but does not actually process them.The short messages remain in the Messages table of the database, wherethey are retrieved by a software component referred to herein as an“Intelligent Delivery Agent” (IDA).

The IDA retrieves messages from the Messages table in the database forsubscribers, e.g., when they power on their handsets, subject to anydesired rules. The IDA can become aware of subscriber power-ups throughany appropriate trigger, e.g., via an SMPP Delivery Receipt mechanism,through Mobile Chat Location Register (MCLR) software, etc. Preferably,the IDA throttles short message traffic to any or all subscribers, e.g.,optionally waiting until the busy hour is over before beginning thetransmission.

The MDC Gateway 100 may be, e.g., a standard WIG to which the providersends messages through SMTP, RMI, HTTP, or suitable middleware software.As shown in FIG. 2, the MDC 100 includes a new DummyDestination, whichsimply acknowledges receipt from a particular subscriber queue 150, butdoes not attempt delivery. Delivery may be accomplished through anIntelligent Delivery Agent process, which polls a messages table that ispopulated when the MDC Gateway 100 receives relevant short messages.

To most efficiently use the MDC gateway 100, the SMTP session preferablyassigns the msgType property based on the sender's Email address andusing InfoProviders information from the database. This allows the MDCGateway 100 to determine that SMTP messages from an Information Provider(e.g., INFO@NEWS.COM) should use the Dummy Destination and be queried bythe IDA. If the short message is submitted via an RMI mechanism, thenthe sender will explicitly define the msgType.

When the MDC 100 inserts a short message record, an Oracle™ trigger maybe used to create a subscriber record in the Subscribers table in thedatabase if such a record does not already exist for the recipient.

The Subscribers table may contain, preferably at a minimum, a MIN,status (e.g., ‘Online’, ‘Offline’, ‘Unknown’), and the time of the laststatus update. When first created, the status may default to ‘Unknown’.

The IDA may be a separate program that delivers messages from thedatabase to appropriate recipients via a RemoteSMPP RMI Interface of thecarrier's gateway. The IDA preferably determines subscriber availabilityvia, e.g., an MCLR or via Delivery Receipts. The former approach islikely more efficient, but the latter approach is more likely to workwith most carrier environments.

The Delivery Receipt method is considered to be more complicated. TheDelivery Receipt method attempts to find the status of a subscriber'shandset by examining delivery receipts from messages sent to thesubscriber.

As shown in FIG. 2, a SubscriberPoller agent 202 starts the process bygathering a list of subscribers from a Subscribers table 214 at sometime interval (z). If a particular subscriber is online, then theDeliveryAgent object 210 is notified.

The DeliveryAgent 210 then gathers some pre-configured number ofmessages in time order for the subscriber from the Messages table 228 inthe database, and sends them to the Carrier gateway 238 for delivery tothe subscriber. There is no delivery receipt associated with thesemessages, so if the subscriber's handset is turned off the shortmessages are not delivered and not resent. This is why it is preferredthat only a pre-configured number of short messages be sent before thesubscriber's status is checked again by SubscriberPoller 202.

If a subscriber's status is unknown, then a DRDeliverAgent 234 isnotified to send one message via the Carrier gateway 238 to thesubscriber with a delivery receipt requested. When it sends the message,it sets the subscriber status as offline so that the SubscriberPoller202 will ignore that subscriber.

The delivery receipt will arrive at DR Listener 208. If the deliveryreceipt indicates failure, then the subscriber status is set as‘unknown’, otherwise the subscriber status is set as ‘online’. TheSubscriberPoller 202 wakes up shortly thereafter to take advantage ofthe user going online.

Because there is no direct feedback from the handset, there is noconventional information received when a handset is turned off or on.DBSubStatusResetter 204 makes assumptions about how long a handsettypically stays on or goes off. If a handset has been marked as onlinefor a period of time (x), then DRSubStatusResetter 204 sets thecorresponding subscriber status to ‘unknown’, which will restart thedelivery receipt cycle again. If a subscriber has been marked as‘offline’ for a different period of time (y), then the subscriber ismarked as unknown, again restarting the delivery receipt cycle.

To summarize, there are three time periods involved in the DeliveryReceipt method. Time x is the average time that a handset is online.Time y is the average time that a handset is offline. Time z is howoften the Subscribers table 214 is polled for a list of subscribers.

The three periods mentioned (x, y, and z) must have a certainrelationship to one another. Time z must be smaller than time x and timey. Time x and time y's relationship to one another doesn't matter. Timez must be smaller than time x so that when a subscriber goes online,messages are sent to it before time x expires and online subscribers areset to ‘unknown’. Time z should be smaller than time y, otherwise thesubscriber will be sent another message before DR Listener 208 has had achance to receive the delivery receipt. This implies that time z willalso be longer than the expected time for a delivery receipt.

A SubscriberCleanUp agent may be implemented to clean out subscribersthat haven't had messages sent to them for a pre-defined period of time.This will ensure that the subscriber database doesn't grow withoutbound. Subscribers may have taken their name from the informationprovider's subscriber list.

Another technique mentioned above is to use an MCLR facility. In thissituation, the MCLR will know explicitly when a handset is turned off oron. The MCLR Listener 218 then updates the Subscribers table 214accordingly. The SubscriberPoller 202 always sees only onlinesubscribers. It then uses the DeliveryAgent 210 to send the messageswithout a delivery receipt requested.

When the MCLR Listener 218 is active, then the DRDeliverAgent 234, DRListener 208, and DBSubStatusResetter 204 are all inactive. When thethree delivery receipt entities are active, then the MCLR Listener 218is inactive.

The IDA Main 232 activates appropriate facilities based on aconfiguration file.

In an MCLR implementation, the DRDeliveryAgent 234, DR Listener 208, andDRSubStatusResetter 204 may not be used.

FIG. 3 is an exemplary class diagram which shows further details of anembodiment of a Message Distribution Center, in accordance with theprinciples of the present invention. In particular, FIG. 3 showsexemplary classes that may be activated and used to determine subscriberstatus and to actually deliver messages.

As shown in FIG. 3, an IDA main class 318 is responsible for decidingwhich subscriber status determination strategy to use. The IDA class 318may receive this information from a configuration file. The IDA class318 instantiates and activates an MCLRListener class 314 if thatfacility is to be used to retrieve a handset's online/offline status. Ifthe strategy is to use delivery receipts, then the IDA class 318 insteadinstantiates and activates the DRListener 322 and DRSubStatusResetter316 classes.

A SubscriberPoller 306 class gets a list of subscribers whose status is‘unknown’ or ‘online’ from the database. If a subscriber's status is‘unknown’, the SubscriberPoller 306 invokes a method in a DeliveryAgentclass 302 to send a message requesting a delivery receipt. If thesubscriber's status is ‘online’, then the DeliveryAgent 302 sendsmessages without a delivery receipt to the subscriber.

The DeliveryAgent 302 is responsible for averaging out the load on thecarrier's system. It may do this by spreading out the messages overtime, allowing normal traffic to be sent more quickly. The DeliveryAgent302 may also hold off sending batch messages during the carrier's busytime. This information may be maintained in a configuration file andretrieved through a DeliverySetupInfo class.

The DeliveryAgent 302 can also be configured to send messages overcertain SMPP ports to the carrier gateway 238 for tracking the amount oftraffic that an information provider is sending. The DeliveryAgent 302may accomplish this by tagging the message with a message typeindicating that it is an MDC message. The configuration file may be setup so that messages of an MDC type will be sent to certain SMPP ports bythe carrier gateway 238.

Both the Subscribers 300 and Messages 304 classes may be wrappers aroundtheir respective database tables, to isolate JDBC calls to these classesonly and/or to place the data in a useful format.

The IDA 318 may send messages and/or decide blackout periods on a globalbasis, i.e., regardless of the destination of any particular message.One enhancement to this is to apply these on a per-carrier basis sincecarriers can be in different time zones or have more or less capablehardware.

One advantage provided by the present invention is that SMTP is awell-known protocol and an easy way for content providers to distributetheir information.

A Message Distribution Center (MDC) in accordance with the principles ofthe present invention provides an ideal solution. It addresses theproblems faced by the carrier without requiring the informationproviders to change technologies.

The principles of the present invention have applicability for usagewith wireless intelligent network (WIN) and SMTP applications, e.g.,those already otherwise containing a Internet gateway application forrouting information through an SMTP gateway. Moreover, the MDC allowscontent providers to continue with their current mode of operationwithout placing the carrier's network at risk. The MDC can receivemessages using a variety of protocols, including SMTP. It automaticallyroutes messages to the appropriate carrier based on MIN range. Insteadof delivering SMTP content directly to the carrier, it is delivered tothe MDC. The MDC then ensures that the content is delivered in a‘carrier-friendly’ manner.

MDC can provide the Info Provider with delivery statistics, e.g., whatpercentage of messages are being delivered.

The MDC helps prevent the carrier from being overwhelmed by bulkmessaging content and provides the following benefits:

-   -   bulk message traffic is distributed across time    -   messages are delivered over more efficient protocols than SMTP        through the carrier's Wireless Internet Gateway    -   messages are only delivered when handsets are on, thereby        eliminating network storage and retries    -   messages are delivered with appropriate urgency, delivery        receipt, expiration times, and billing identifiers    -   individual bulk message queues allow the carrier to limit the        number of messages that can be queued per subscriber    -   bulk messaging can be disabled for individual accounts when        subscribers churn    -   bulk message delivery statistics are available to the carrier        via a web interface.

Acknowledgement of Delivery Receipts

It is preferred that remote gateways be sent to via a remote queue. Thisis because of the uncertainty about the link IDs which would be used bythe remote gateway per MIN. Rather, all that is known is that a gatewaytakes a certain range of MINs. However, the gateway itself may partitionout the MINs to be sent via different protocols such as SMPP, TNPP orothers. That information is preferably not kept at the IDA 318,preventing use of the remote SMPP classes. However, the remote queue hasno provision for sending information back. It is preferred that thisability be provided so as to receive back delivery receipts.

In accordance with the principles of the present invention, aReceiptNotifier class may be added to the code. When such aReceiptNotifier class detects that a delivery receipt is to go back tothe IDA 318 (i.e., a hostname or IP is in receiptEmail, receiptMIN or anew receipt field in the Message class 304), it establishes a connectionwith the IDA 318 and sends back the receipt information.

Two exemplary methods to receive back at the IDA 318 the deliveryreceipt, both involving gateway software running at a remote site torecognize first that a delivery receipt is necessary. One was discussedabove, while the other establishes a connection back to the IDA 318 anda protocol to use. In accordance with the principles of the presentinvention, RMI techniques may be used to accomplish this.

When the remote gateway sees an IDA delivery receipt request, it mayperform a Naming.lookup( ) based on the URL in the delivery receiptfield in the Message. It then sends the message name field from theMessage and the delivery status. Once sent, it can abandon the object itgot back from the Naming.lookup( ) call.

This implies that the remote gateway will be an RMI client to the IDAdelivery receipt server. Typically the remote gateway has been acting asan RMI server. However, this scheme of being a client falls in line withhow the SMTP delivery receipt is sent, that is, the remote gateway actsas a mail client in this case.

An IReceiptProxy interface 322 may be added to allow communicationbetween the MDC gateway 100 and the IDA 318. The DRListener agent 322 inthe IDA 318 preferably acts as an RMI server to receive theacknowledgements from the MDC gateway class ReceiptNotifier. ThereceiptEmail field in the Message preferably contains the hostname torespond back to. ReceiptNotifier distinguishes between email addressesand host names in this field and sends the delivery receipt accordingly.

The IDA 318 is configured via appropriate configuration files, e.g., anida.cfg file, an IdaRemoteHostInfo.properties file, and database tables(described more fully herein below). It is preferred that the IDA 318use the same database as the MDC gateway 100. The MDC gateway 100 andthe IDA 318 preferably utilize tables and configuration/property files,which should be set up correctly. In operation, the setup of MDC and IDAconfiguration/property files is typically the responsibility of an MDCadministrator. Exemplary values for configurable files are providedherein below.

The MDC 100 and IDA 318 work together to handle the large amount oftraffic generated by information providers. The MDC 100 automaticallyroutes messages to the IDA 318 based on if the message is from aninformation provider. Instead of delivering SMTP content directly to thecarrier, the MDC 100 delivers it to the IDA 318. The IDA 318 thenensures that the content is delivered in a ‘carrier-friendly’ manner.

The MDC Gateway 100 is started using a standard smsgw.sh script. The IDA318 may be started separately with an ida.sh script. The only necessarydependency between the two programs is the database tables they share.This means that either can be started without the other running.However, nothing useful happens until both are running.

Table 1 describes relevant modules in the MDC Gateway 100.

TABLE 1 Module Name Package Base36.java tcs.ain.smsgw Config.javatcs.ain.smsgw DummyDestination.java tcs.ain.smsgw IReceiptProxy.javatcs.ain.smsgw Message.java tcs.ain.smsgw MessageStoreDB.javatcs.ain.smsgw ReceiptNotifier.java tcs.ain.smsgw SMPPReceiptMessage.javatcs.ain.smpp SMPPResource.java tcs.ain.smpp SMTPMessageData.javatcs.ain.smsgw SMTPSession.java tcs.ain.smsgw

Table 2 identifies relevant exemplary modules in an IDAm 318, packed inthe exemplary embodiment in a “tcs.ain.ida” package and located in adirectory in the MDC gateway 100, e.g., called “smswebgw”.

TABLE 2 Module Name DRListener.java DRSubStatusResetter.javaDeliveryAgent.java HostInfo.java IDA.java IDAConfig.java IdaDebug.javaInfoProviders.java MCLRListener.java Messages.java RemoteGwInfo.javaSubscriberInfo.java SubscriberPoller.java Subscribers.java

The MDC Gateway 100 uses a number of database tables. The following areexemplary configurable tables 500 specifically used by the MDC Gateway100 and the IDA 318.

INFOPROVIDER Configuration Table

An INFOPROVIDER table provides a list of information providers. If aninformation provider is on this list, the MDC Gateway 100 will route arelevant message to the IDA 318. The INFOPROVIDER table is used only bythe MDC Gateway 100.

The INFOPROVIDER table is preferably configured by an appropriate systemadministrator.

TABLE 3 Column Data Type Null? Notes MSGSENDER CHAR(150) N Should matchwhat the information provider puts inthe sender field in mail LASTUPDATENUMBER Y Currently unused. Should represent time when row was insertedINFOPROVIDERID NUMBER(9) Y PROVIDERNAME VARCHAR2(50) Y SERVERIDVARCHAR(50) Y SERVERPASSWORD VARCHAR2(50) Y

LINKID NPANXX Configuration Table

A LINKID_NPANXX configurable table, used by both the MDC gateway 100 andthe IDA 318 associates a MIN with a carrier's remote gateway. Link IDsare defined for each carrier in a GWDest.properties file fromsmswebgw/smsgw. The IdaRemoteHostInfo.properties file mentioned in thenext section should align with the link IDs.

The LINKID_NPANXX table is preferably configured by an appropriateadministrator.

TABLE 4 Column Data Type Null? Notes LINKID NUMBER(2) Y This number isan ID assigned to each carrier with a remote gateway to which the IDAcan send messages. NPA_NXX VARCHAR2(6) N Represents the first 6 digitsof a MIN and is used to assign a MIN to a remote gateway.

MESSAGES Configuration Table

A MESSAGES table contains information about a message being sent. TheMESSAGES table may be used by both the MDC gateway 100 and the IDA 318.

TABLE 5 Column Data Type Null? MSGTYPE NUMBER(2) Y MSGSOURCE NUMBER(2) YMSGSTATUS NUMBER(2) Y MSGSUBSTATUSDESC VARCHAR2(255) Y MSGMINVARCHAR2(30) Y MSGCALLBACK VARCHAR2(30) Y MSGSENDER VARCHAR2(150) YMSGSUBJECT VARCHAR2(255) Y MSGTEXT VARCHAR2(2000) Y MSGSRCADDRVARCHAR2(150) Y SMSCMSGID VARCHAR2(10) Y RECEIPTEMAIL VARCHAR2(70) YRECEIPTMIN VARCHAR2(30) Y RECEIPTCALLBACK VARCHAR2(30) Y MSGNAME (theunique VARCHAR2(20 N identifier (key)) SRCGWID VARCHAR2(5) Y MSGARRIVENUMBER Y MSGSENT NUMBER Y MSGFINAL NUMBER Y MSGSUBMIT NUMBER Y MSGEXPIRENUMBER Y

SUBSCRIBERS Configuration Table

A SUBSCRIBERS table is used internally by the IDA 318. It keeps track ofsubscribers that have been sent messages by an information provider. TheSUBSCRIBERS table is used by both the MDC Gateway 100 and the IDA 318.

TABLE 6 Column Data Type Null? Notes SUBSCRIBERMIN VARCHAR2(30) N STATUSNUMBER(2) N Internal value (0—offline, 1—online, 2—unknown)LASTSTATUSUPDATE NUMBER Y Last time the status TIME was changedLASTMSGTIME NUMBER Y Last time the subscriber received a message

There is only one trigger in the exemplary embodiments defined for theIDA 318, called subsc_update. Whenever a message is added to theMESSAGES table, the subscriber is added or updated in the SUBSCRIBERStable if the message is from an information provider. This may beindicated, e.g., by bit 6 being set in an msgsource field.

IDA Configuration File

An ida.cfg file contains parameters that control the behavior of the IDAprogram 318. It is preferred that the ida.cfg file reside in the samedirectory as the executing IDA program 318. Table 7 shows exemplaryparameters and values of an ida.cfg file, in accordance with theprinciples of the present invention.

TABLE 7 Parameter Purpose Field Value Field Explanation GeneralParameters SubscriberStrategy Strategy used to DELIVERY_RECEIPT Have theremote find subscriber (default) gateway request a status deliveryreceipt MCLR Use mobile chat location register (not implemented yet)debugmode Used to set the true Turn on run-time IDA to print run-messages time debug false (default) Turn off run-time messages messagesRemoteQueueName Name of remote RemoteQueue Only changed for queue tosend (default) debugging messages to purposes DRServerName Name ofservice DeliveryReciptServer Only changed for to receive deliverydebugging receipts purposes LogFileName Name of file to text stringAbsolute or receive log relative path to a messages logger fileDirectory must exist already. Database Parameters DbClass The driver touse text string Class name to use for talking with the for databasedatabase access. System must be configured with proper drivers DbUrl Thereference to text string Legal URL for the the database and drivermachine where database resides DbAccount Account name text stringDbPassword Password to text string account Delivery Setup ParametersMsgGroupSize Number of number messages to send to a subscriber at a timeMsgSendRate Number of number messages to send per minute MsgHoldTimesTime to not send Start time and Must have start msgs (local time). endtime in 24 and end times. If Repeat the line hour format, end is lessthan for multiple HHMM start, then cross periods over of midnight isassumed. Polling/Expiration Rates Parameters SubscriberOnlineTimeMaximum number number of seconds a subscriber stays onlineSubscriberOfflineTime Maximum number number of seconds a subscriberstays offline SubscriberXmitPoll Time between number This must be lessTime checks for than half the value subscriber of the smaller ofmessages SubscriberOnlineTime & (seconds) SubscriberOfflineTimeSubscriberExpireTime Hours without a number message before a subscriberis purged.IdaRemoteHostInfo.properties File

This file relates a link ID for a MIN to a remote host name, and whetherit can support delivery receipts. A leading number followed by anunderscore corresponds to the link ID in the LINKID_NPANXX table and theGWDest.properties file.

The form of an entry in the disclosed IdaRemoteHostInfo.properties filemay be, e.g., <linkid>_<parameter>=value. Permissible parameters andtheir values for the exemplary IdaRemoteHostInfo.properties files areshown in Table 8.

TABLE 8 Parameter Purpose Values carrierName Short form of the carrierText string name carrierNameLong Long form of the carrier Text stringname carrierHostname The host name of the The name must be machine withthe carrier's resolvable via DNS. remote gateway receiptSupportedIndicates if remote true, yes, false or no gateway can send deliveryreceipts. The gateway must be running the updated version of TCS gatewaysoftware and have enable_web in smscgw.cfg set to true

Table 9 is an example showing how the carrier data may be formatted inthe IdaRemoteHostInfo.properties file.

TABLE 9 0_carrierName=AT 0_carrierNameLong=AirTouch0_carrierHostname=Sms2way.airtouch.net 0_receiptSupported=yes3_carrierName=BAM 3_carrierNameLong=Bell Atlantic Mobile3_carrierHostname=smsc.bam.com 3_receiptSupported=yes 24_carrierName=FR24_carrierNameLong=Frontier 24_carrierHostname=msg.frontiercellular.com24_receiptSupported=no

MDC Configuration File

An smscgw.cfg file may be used to configure the software of the MDCGateway 100. The disclosed MDC Gateway 100 requires several parametersto be set to route short messages from information providers to the IDA318. The Remote Gateways that the IDA 318 talks to preferably have aflag such as “enable_web” set if they are to be capable of sendingdelivery receipts back to the IDA 318. Tables 10 and 11 show exemplaryparameters in an MDC Configuration File, in accordance with theprinciples of the present invention.

TABLE 10 smscgw.cfg MDC Gateway Configuration Parameter MDC Value Notesenable_mdc yes Causes check for information provider messagesenable_smtp yes Remote gateway routes mail to the IDA. enable_web yesAllows remote queue calls via RMI MessageStore DB IDA can only work withdatabase Type activated

TABLE 11 smscgw.cfg Remote Gateway Configuration Parameter MDC ValueNotes enable_web yes Allows remote queue calls via RMI

While the invention has been described with reference to the exemplaryembodiments thereof, those skilled in the art will be able to makevarious modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

1. A method of providing cross-carrier messaging, comprising:intercepting a short message from sending subscriber of a first wirelesscarrier intended for transmission over an Internet; storing saidintercepted short message in an individual subscriber queue located in agateway; determining a destination of said short message based on amobile identification number (NIM); and automatically delivering saidshort message to said receiving subscriber of a second wireless carrierdifferent from said first wireless carrier without transmission oversaid Internet; whereby said short message is transmitted betweendifferent wireless carriers without requiring transmission over anInternet. 2-10. (canceled)